Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17569362422887c138a81919beaf919b39504e89a6d0cccb03bc6472999ac571

Tx prefix hash: f8c949e35b4e731b2a4b503d1522071f22994440e80fb3390b14674eb05ebdfb
Tx public key: eed055c6128d921c22d8ce3a4f526d765a5df4cec5a090444f76945b01960f10
Timestamp: 1669500736 Timestamp [UCT]: 2022-11-26 22:12:16 Age [y:d:h:m:s]: 02:172:19:37:13
Block: 639789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 645255 RingCT/type: yes/0
Extra: 01eed055c6128d921c22d8ce3a4f526d765a5df4cec5a090444f76945b01960f10021100000001faf35c9c000000000000000000

1 output(s) for total of 4.657077395000 dcy

stealth address amount amount idx
00: 203b0937f0bbd46d8c9691e03e07b80e8d3532f25f6ed875303d13671b5b1c0b 4.657077395000 1079464 of 0

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": 639799, "vin": [ { "gen": { "height": 639789 } } ], "vout": [ { "amount": 4657077395, "target": { "key": "203b0937f0bbd46d8c9691e03e07b80e8d3532f25f6ed875303d13671b5b1c0b" } } ], "extra": [ 1, 238, 208, 85, 198, 18, 141, 146, 28, 34, 216, 206, 58, 79, 82, 109, 118, 90, 93, 244, 206, 197, 160, 144, 68, 79, 118, 148, 91, 1, 150, 15, 16, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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