Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c73d520f0d13f2b5638e3c988971d2fbf6907c6cfdd6a6ab6b47461e6117619c

Tx prefix hash: 7990e3fe85c6e096cb64df125d1cf70ef657bb5da19629f24778064b2121d15b
Tx public key: a820dd3b1176a6777f1f1c098924fe77735a0122d1714fd4304ed3d110f31f4b
Timestamp: 1657632004 Timestamp [UCT]: 2022-07-12 13:20:04 Age [y:d:h:m:s]: 03:111:06:12:59
Block: 542195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 859230 RingCT/type: yes/0
Extra: 01a820dd3b1176a6777f1f1c098924fe77735a0122d1714fd4304ed3d110f31f4b0211000000012e6b1fd5000000000000000000

1 output(s) for total of 9.805800040000 dcy

stealth address amount amount idx
00: 6671b2870abbf2e33e86b975e228719ffb7d4298c15ba37165e84576472fdbf8 9.805800040000 972724 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": 542205, "vin": [ { "gen": { "height": 542195 } } ], "vout": [ { "amount": 9805800040, "target": { "key": "6671b2870abbf2e33e86b975e228719ffb7d4298c15ba37165e84576472fdbf8" } } ], "extra": [ 1, 168, 32, 221, 59, 17, 118, 166, 119, 127, 31, 28, 9, 137, 36, 254, 119, 115, 90, 1, 34, 209, 113, 79, 212, 48, 78, 211, 209, 16, 243, 31, 75, 2, 17, 0, 0, 0, 1, 46, 107, 31, 213, 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