Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ee7b06dfa75ed7f853f2d35ec4c15833a46b297fa1384900cc4759359d63078

Tx prefix hash: 48d3fdee39df0b71e79495f2591bd00320437a07ec91c2c6040b9fe238a5cea8
Tx public key: bbf43ae6368c4009c9a0a5171f03ec2432e57bfad87e1243289f74406ef3c9c9
Timestamp: 1715939893 Timestamp [UCT]: 2024-05-17 09:58:13 Age [y:d:h:m:s]: 00:233:17:45:00
Block: 1023897 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167295 RingCT/type: yes/0
Extra: 01bbf43ae6368c4009c9a0a5171f03ec2432e57bfad87e1243289f74406ef3c9c902110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2fee6f87e5deb311d9d73f6c0d4188e2f6ebe1e43f382a47df928a59632995c 0.600000000000 1489220 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": 1023907, "vin": [ { "gen": { "height": 1023897 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2fee6f87e5deb311d9d73f6c0d4188e2f6ebe1e43f382a47df928a59632995c" } } ], "extra": [ 1, 187, 244, 58, 230, 54, 140, 64, 9, 201, 160, 165, 23, 31, 3, 236, 36, 50, 229, 123, 250, 216, 126, 18, 67, 40, 159, 116, 64, 110, 243, 201, 201, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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