Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc81ff94841dc516cb0f62c1a24ea2cd2295723099b08414544f027de764050b

Tx prefix hash: 98a44022634f793f9d5cb686aa4839b721e802f0349c987c61619049b81fc5a1
Tx public key: 52af9f93b830874a502bd6073c503248f99613e9af4e5996fd6b209a0be6a0cf
Timestamp: 1711027593 Timestamp [UCT]: 2024-03-21 13:26:33 Age [y:d:h:m:s]: 01:086:16:30:41
Block: 983192 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322859 RingCT/type: yes/0
Extra: 0152af9f93b830874a502bd6073c503248f99613e9af4e5996fd6b209a0be6a0cf02110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60ec3ffc559b1f8b3476d40e4f0740d6417a841163e86e09ace0f356b332ffa0 0.600000000000 1443319 of 15

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": 983202, "vin": [ { "gen": { "height": 983192 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60ec3ffc559b1f8b3476d40e4f0740d6417a841163e86e09ace0f356b332ffa0" } } ], "extra": [ 1, 82, 175, 159, 147, 184, 48, 135, 74, 80, 43, 214, 7, 60, 80, 50, 72, 249, 150, 19, 233, 175, 78, 89, 150, 253, 107, 32, 154, 11, 230, 160, 207, 2, 17, 0, 0, 0, 10, 0, 17, 5, 91, 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