Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96e261ceb9a08bbd91b5efa5f5f7600d3b052cb6291ff22c54f69ce8e926015f

Tx prefix hash: 9c22426091c8f9f9aad485332352137dfa50b8df223ef817e3c2248f7bcbbd5b
Tx public key: e3c58e9f0576bb89eea1469bcaee58da172cb3d6fd0930dd4a8f4730713710b5
Timestamp: 1746941945 Timestamp [UCT]: 2025-05-11 05:39:05 Age [y:d:h:m:s]: 00:141:13:12:43
Block: 1280388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98796 RingCT/type: yes/0
Extra: 01e3c58e9f0576bb89eea1469bcaee58da172cb3d6fd0930dd4a8f4730713710b502110000000601491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa8d8bf12998f890b56b8ac48ce879febe4492536205982fde96c40d8ae986bf 0.600000000000 1767773 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": 1280398, "vin": [ { "gen": { "height": 1280388 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa8d8bf12998f890b56b8ac48ce879febe4492536205982fde96c40d8ae986bf" } } ], "extra": [ 1, 227, 197, 142, 159, 5, 118, 187, 137, 238, 161, 70, 155, 202, 238, 88, 218, 23, 44, 179, 214, 253, 9, 48, 221, 74, 143, 71, 48, 113, 55, 16, 181, 2, 17, 0, 0, 0, 6, 1, 73, 31, 136, 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