Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b2b1ee956bd41a5af4193403704e377bf144cc7a3cab2776fd104aaaf6f6e30

Tx prefix hash: b0080b37d840a56276e14de04261784b0d680e368a9ceb27ff069ac71e951c8b
Tx public key: 38afba179a0a2df27a54978e37afdecb517c70e5b60fecb397878955ad8769a0
Timestamp: 1649507037 Timestamp [UCT]: 2022-04-09 12:23:57 Age [y:d:h:m:s]: 02:304:10:05:00
Block: 476542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 737119 RingCT/type: yes/0
Extra: 0138afba179a0a2df27a54978e37afdecb517c70e5b60fecb397878955ad8769a0021100000016bf7ee4e7000000000000000000

1 output(s) for total of 16.181499788000 dcy

stealth address amount amount idx
00: b5ee1df870f2e806618b5a28e1f1f08b90c61071ef77f30ad338d1ece31ec5df 16.181499788000 897033 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": 476552, "vin": [ { "gen": { "height": 476542 } } ], "vout": [ { "amount": 16181499788, "target": { "key": "b5ee1df870f2e806618b5a28e1f1f08b90c61071ef77f30ad338d1ece31ec5df" } } ], "extra": [ 1, 56, 175, 186, 23, 154, 10, 45, 242, 122, 84, 151, 142, 55, 175, 222, 203, 81, 124, 112, 229, 182, 15, 236, 179, 151, 135, 137, 85, 173, 135, 105, 160, 2, 17, 0, 0, 0, 22, 191, 126, 228, 231, 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