Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af3a6e367109e0481cd8d82cd23a541fdab790a5da89a36fd60a4382b4f65dfc

Tx prefix hash: d5091225d6b9c2d820027667dbd25526e4b8cfb4a1c941c8759201aa1a9b6250
Tx public key: f2f7abb49768db160c9dcf02771e3d218288f2d7d9a56167f10d02f9221e5c13
Timestamp: 1735414080 Timestamp [UCT]: 2024-12-28 19:28:00 Age [y:d:h:m:s]: 00:327:15:03:43
Block: 1185212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231677 RingCT/type: yes/0
Extra: 01f2f7abb49768db160c9dcf02771e3d218288f2d7d9a56167f10d02f9221e5c130211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61d6ca8fad9ce0b071475707348a8fca9cb35eaff0900ed0162913b7be202fdf 0.600000000000 1671679 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": 1185222, "vin": [ { "gen": { "height": 1185212 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61d6ca8fad9ce0b071475707348a8fca9cb35eaff0900ed0162913b7be202fdf" } } ], "extra": [ 1, 242, 247, 171, 180, 151, 104, 219, 22, 12, 157, 207, 2, 119, 30, 61, 33, 130, 136, 242, 215, 217, 165, 97, 103, 241, 13, 2, 249, 34, 30, 92, 19, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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