Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 555da9536809a83e5da617d705064dba9e4ff59a7cfc2e12b380725edd4dde8a

Tx prefix hash: 53c7565330602a451a6d3ffd3cb5f428885094a785f1e34cf75a8fd9d8ac328a
Tx public key: 60cf11e3deb005f013687b5226a02f1ba47d39b1b4c72cae8285e4aff49e43fd
Timestamp: 1705550272 Timestamp [UCT]: 2024-01-18 03:57:52 Age [y:d:h:m:s]: 01:082:05:37:41
Block: 937732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319880 RingCT/type: yes/0
Extra: 0160cf11e3deb005f013687b5226a02f1ba47d39b1b4c72cae8285e4aff49e43fd02110000000e7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88784209cbe4b76d1f71c5258d961e8da44e375bc5a0ab766c62f54cb4106f14 0.600000000000 1395794 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": 937742, "vin": [ { "gen": { "height": 937732 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88784209cbe4b76d1f71c5258d961e8da44e375bc5a0ab766c62f54cb4106f14" } } ], "extra": [ 1, 96, 207, 17, 227, 222, 176, 5, 240, 19, 104, 123, 82, 38, 160, 47, 27, 164, 125, 57, 177, 180, 199, 44, 174, 130, 133, 228, 175, 244, 158, 67, 253, 2, 17, 0, 0, 0, 14, 122, 156, 244, 199, 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