Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 091499f547b1bc188259141e5e42ab11a1b6afadd9c925fc5e787dffc1d8327c

Tx prefix hash: d672e74b5605b886259be1581e841ec950f313ccdb8159c2362fb816edd62c0f
Tx public key: 6465c9c56f6fada71a9de5c040cd6d450392710bab1a6a8d047283cadc423d9e
Timestamp: 1712760797 Timestamp [UCT]: 2024-04-10 14:53:17 Age [y:d:h:m:s]: 00:358:11:28:46
Block: 997514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256297 RingCT/type: yes/0
Extra: 016465c9c56f6fada71a9de5c040cd6d450392710bab1a6a8d047283cadc423d9e0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1d1bc4401d2befdbb8a634eb893e097c403f97d1e9606d0d31f5cf18a70b63d 0.600000000000 1457946 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": 997524, "vin": [ { "gen": { "height": 997514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1d1bc4401d2befdbb8a634eb893e097c403f97d1e9606d0d31f5cf18a70b63d" } } ], "extra": [ 1, 100, 101, 201, 197, 111, 111, 173, 167, 26, 157, 229, 192, 64, 205, 109, 69, 3, 146, 113, 11, 171, 26, 106, 141, 4, 114, 131, 202, 220, 66, 61, 158, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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