Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 156be49223dd968c2fe4e0f5ef3bb4e12a9ba2648a1eb102d54bfc5e450916ce

Tx prefix hash: 59f8a2c895bcd8c12148bd74c03836e33143ed880194fc967e9b147d5865a170
Tx public key: 8e0894bc0711433a06a61a8f5d5e93a9d83c1fb002b5b332ab62a41daebc2397
Timestamp: 1711493441 Timestamp [UCT]: 2024-03-26 22:50:41 Age [y:d:h:m:s]: 01:006:07:11:35
Block: 987056 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265432 RingCT/type: yes/0
Extra: 018e0894bc0711433a06a61a8f5d5e93a9d83c1fb002b5b332ab62a41daebc239702110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a91646c79c08592c9ccee872be1a5e501f2cb27e48b23a656f8c1ff6d0dc5588 0.600000000000 1447297 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": 987066, "vin": [ { "gen": { "height": 987056 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a91646c79c08592c9ccee872be1a5e501f2cb27e48b23a656f8c1ff6d0dc5588" } } ], "extra": [ 1, 142, 8, 148, 188, 7, 17, 67, 58, 6, 166, 26, 143, 93, 94, 147, 169, 216, 60, 31, 176, 2, 181, 179, 50, 171, 98, 164, 29, 174, 188, 35, 151, 2, 17, 0, 0, 0, 9, 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