Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de4d322f2ac230866c22ca9837c71a7932bf4220a90d8f480df67914f839bcf7

Tx prefix hash: a975e096e158f2a209edb372d6c4c45259a391496550291939c90471cbc0a63d
Tx public key: 6a5f35c30327c1b3d95e716dc65a350a14b7cf8db1614e5647e98f751bda6867
Timestamp: 1715558700 Timestamp [UCT]: 2024-05-13 00:05:00 Age [y:d:h:m:s]: 00:243:06:14:44
Block: 1020764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174084 RingCT/type: yes/0
Extra: 016a5f35c30327c1b3d95e716dc65a350a14b7cf8db1614e5647e98f751bda686702110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef078a3a4b297c8fb14ae8779099e231f6534078098c770998c033c114cea9f9 0.600000000000 1484853 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": 1020774, "vin": [ { "gen": { "height": 1020764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef078a3a4b297c8fb14ae8779099e231f6534078098c770998c033c114cea9f9" } } ], "extra": [ 1, 106, 95, 53, 195, 3, 39, 193, 179, 217, 94, 113, 109, 198, 90, 53, 10, 20, 183, 207, 141, 177, 97, 78, 86, 71, 233, 143, 117, 27, 218, 104, 103, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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