Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 044b5009f4f20444b073ca1db56f6a44dbd86be883876d9ae5508d28065a30a5

Tx prefix hash: 85d8217bbbe4a05007660d64c0e4dbc68f4137793dff8c1ff77b3096fdcccff2
Tx public key: 94f7605068b254f9de6eb90d1d7ef97bf30fdf0a7c1941ad2c231655c3ea065d
Timestamp: 1577798823 Timestamp [UCT]: 2019-12-31 13:27:03 Age [y:d:h:m:s]: 05:164:21:05:06
Block: 35782 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1267609 RingCT/type: yes/0
Extra: 0194f7605068b254f9de6eb90d1d7ef97bf30fdf0a7c1941ad2c231655c3ea065d0211000000214ac5aa02000000000000000000

1 output(s) for total of 467.132661678000 dcy

stealth address amount amount idx
00: e5b2dca3ddaac3a38279ea1d7fce5959c38c9507a9b1bc1e5bcd47abf6f4107a 467.132661678000 60412 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 35792, "vin": [ { "gen": { "height": 35782 } } ], "vout": [ { "amount": 467132661678, "target": { "key": "e5b2dca3ddaac3a38279ea1d7fce5959c38c9507a9b1bc1e5bcd47abf6f4107a" } } ], "extra": [ 1, 148, 247, 96, 80, 104, 178, 84, 249, 222, 110, 185, 13, 29, 126, 249, 123, 243, 15, 223, 10, 124, 25, 65, 173, 44, 35, 22, 85, 195, 234, 6, 93, 2, 17, 0, 0, 0, 33, 74, 197, 170, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8