Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cca18aa2502fd8412bff91da718bdacda2daa2ed8fb492788877a4f574d265d

Tx prefix hash: a0e2a3b1c8cf16230e3df18312005eaf7f284ba83c41e0dfeffc28e24629aaed
Tx public key: 82301a4bf9c0d44f2044509b3a2c7bb41fc2c1e75029fa37caca51c98d24f887
Timestamp: 1724645761 Timestamp [UCT]: 2024-08-26 04:16:01 Age [y:d:h:m:s]: 01:071:01:12:13
Block: 1096068 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309209 RingCT/type: yes/0
Extra: 0182301a4bf9c0d44f2044509b3a2c7bb41fc2c1e75029fa37caca51c98d24f88702110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b960d9923e2c6c12ecc00677f89656dc5c88d4b7cb1c248af1774e55bc781a8c 0.600000000000 1571255 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": 1096078, "vin": [ { "gen": { "height": 1096068 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b960d9923e2c6c12ecc00677f89656dc5c88d4b7cb1c248af1774e55bc781a8c" } } ], "extra": [ 1, 130, 48, 26, 75, 249, 192, 212, 79, 32, 68, 80, 155, 58, 44, 123, 180, 31, 194, 193, 231, 80, 41, 250, 55, 202, 202, 81, 201, 141, 36, 248, 135, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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