Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22dd35e3ff716bae6fa1f0247ccb54ea98386dad66290179d2a742e2f6833e02

Tx prefix hash: 52bdf2432d806b17ce984fdec8328ebb588e22e0f5c824adb4e35cb967b8a2a5
Tx public key: 447e4a99d22ea9349c5f42cab25ba9b96ebfc28a55ab2ecd8dcfa5e9566674de
Timestamp: 1738484341 Timestamp [UCT]: 2025-02-02 08:19:01 Age [y:d:h:m:s]: 00:330:10:08:00
Block: 1210370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233970 RingCT/type: yes/0
Extra: 01447e4a99d22ea9349c5f42cab25ba9b96ebfc28a55ab2ecd8dcfa5e9566674de021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c6097d1b337026f1d8309d7796ec6b1ed33b145b49eaa9835060e888562d0ce 0.600000000000 1697121 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": 1210380, "vin": [ { "gen": { "height": 1210370 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c6097d1b337026f1d8309d7796ec6b1ed33b145b49eaa9835060e888562d0ce" } } ], "extra": [ 1, 68, 126, 74, 153, 210, 46, 169, 52, 156, 95, 66, 202, 178, 91, 169, 185, 110, 191, 194, 138, 85, 171, 46, 205, 141, 207, 165, 233, 86, 102, 116, 222, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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