Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1dbce7bb442ca59246c2a2f87fa458ad118f64be87727814cbc2460d69a3ed96

Tx prefix hash: bc6042eec94a4780c6d704b17fd15b712a01802ee8a3f7ce9a5c7e8a9b411665
Tx public key: 66df1ddd40e40c4a47c2b148cd1d80382f626603dd5722bb839c8c55dea6098a
Timestamp: 1707878498 Timestamp [UCT]: 2024-02-14 02:41:38 Age [y:d:h:m:s]: 01:056:20:17:44
Block: 957052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301674 RingCT/type: yes/0
Extra: 0166df1ddd40e40c4a47c2b148cd1d80382f626603dd5722bb839c8c55dea6098a02110000000e0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aae46d4fdf81e9062fccac8053dd153fcfae98885bea71239084560b564f1671 0.600000000000 1416366 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": 957062, "vin": [ { "gen": { "height": 957052 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aae46d4fdf81e9062fccac8053dd153fcfae98885bea71239084560b564f1671" } } ], "extra": [ 1, 102, 223, 29, 221, 64, 228, 12, 74, 71, 194, 177, 72, 205, 29, 128, 56, 47, 98, 102, 3, 221, 87, 34, 187, 131, 156, 140, 85, 222, 166, 9, 138, 2, 17, 0, 0, 0, 14, 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