Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e702cd5d2016e35656b849a8af0f6cd0e10a95b23472e531cc8acef846183682

Tx prefix hash: d034c0e507e6c3b814a04204afe49f62d0590bdcabbc06cd8e011820f4929cee
Tx public key: c6dcf784061cd1caa5b208069bb57f94505574d2965b8f1f8c99be2734941264
Timestamp: 1639042146 Timestamp [UCT]: 2021-12-09 09:29:06 Age [y:d:h:m:s]: 03:061:14:43:55
Block: 391678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 822750 RingCT/type: yes/0
Extra: 01c6dcf784061cd1caa5b208069bb57f94505574d2965b8f1f8c99be2734941264021100000004a272b9cb000000000000000000

1 output(s) for total of 30.922258066000 dcy

stealth address amount amount idx
00: b35d174a47bfd286af3ac0e8d989707774048a5bf091ed8dc30dda9dcba165c3 30.922258066000 788167 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": 391688, "vin": [ { "gen": { "height": 391678 } } ], "vout": [ { "amount": 30922258066, "target": { "key": "b35d174a47bfd286af3ac0e8d989707774048a5bf091ed8dc30dda9dcba165c3" } } ], "extra": [ 1, 198, 220, 247, 132, 6, 28, 209, 202, 165, 178, 8, 6, 155, 181, 127, 148, 80, 85, 116, 210, 150, 91, 143, 31, 140, 153, 190, 39, 52, 148, 18, 100, 2, 17, 0, 0, 0, 4, 162, 114, 185, 203, 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