Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b62f59fc1adbd2bb832b01642a0404af76dfbbf2e4947120a4929e7a5631b8fa

Tx prefix hash: 68f08124c865cf4cef7fbea81f30517126f466b316266ef8be59956177a8b276
Tx public key: 5f9aea8b441075115e2d3159156a82523fc46aa22bc91498be45dfe18cb1526b
Timestamp: 1722436437 Timestamp [UCT]: 2024-07-31 14:33:57 Age [y:d:h:m:s]: 00:249:01:26:36
Block: 1077749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177904 RingCT/type: yes/0
Extra: 015f9aea8b441075115e2d3159156a82523fc46aa22bc91498be45dfe18cb1526b02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63d5def8bb9d24e3fe9c0bd8b1ef08cef30e9b6f890efdc4b08c4611b8958cb6 0.600000000000 1550304 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": 1077759, "vin": [ { "gen": { "height": 1077749 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63d5def8bb9d24e3fe9c0bd8b1ef08cef30e9b6f890efdc4b08c4611b8958cb6" } } ], "extra": [ 1, 95, 154, 234, 139, 68, 16, 117, 17, 94, 45, 49, 89, 21, 106, 130, 82, 63, 196, 106, 162, 43, 201, 20, 152, 190, 69, 223, 225, 140, 177, 82, 107, 2, 17, 0, 0, 0, 1, 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