Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93d7a87e1533261b35e43af05389c361c0e6243b073c31450ffddc6926e8a65f

Tx prefix hash: 99dfb1790549a54acb30029094a08f7fdebad8a9d276d2a60dc486499f41f4c7
Tx public key: c0f213cab41e6494ddf9ae0cc51ea5f90c933035e11b2502a5b96050cf4d1439
Timestamp: 1706412672 Timestamp [UCT]: 2024-01-28 03:31:12 Age [y:d:h:m:s]: 01:072:00:53:41
Block: 944884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312570 RingCT/type: yes/0
Extra: 01c0f213cab41e6494ddf9ae0cc51ea5f90c933035e11b2502a5b96050cf4d143902110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d38818d103260ac086dac88fb564a3424d61f341f8766dd1048856a619c13fb 0.600000000000 1403178 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": 944894, "vin": [ { "gen": { "height": 944884 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d38818d103260ac086dac88fb564a3424d61f341f8766dd1048856a619c13fb" } } ], "extra": [ 1, 192, 242, 19, 202, 180, 30, 100, 148, 221, 249, 174, 12, 197, 30, 165, 249, 12, 147, 48, 53, 225, 27, 37, 2, 165, 185, 96, 80, 207, 77, 20, 57, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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