Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e14cb34298cb863b188689d1e8dadedf119ef8c4dece67073039c313fbf3b0f

Tx prefix hash: 7a2a496a54c2610df16da7aa9a580a671d1f6ba603cb8e874a0ab2c3013a5940
Tx public key: 056802743a360c62d927fd7dcc5cd3290d3e21ee4854a477a3bda354d11ba010
Timestamp: 1734960072 Timestamp [UCT]: 2024-12-23 13:21:12 Age [y:d:h:m:s]: 00:095:13:06:46
Block: 1181494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68038 RingCT/type: yes/0
Extra: 01056802743a360c62d927fd7dcc5cd3290d3e21ee4854a477a3bda354d11ba010021100000005d4a401e0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59a293428dd27078d2207c6a8db3237cd1bb19bc59cd077a56c9e6355ab54107 0.600000000000 1667919 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": 1181504, "vin": [ { "gen": { "height": 1181494 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59a293428dd27078d2207c6a8db3237cd1bb19bc59cd077a56c9e6355ab54107" } } ], "extra": [ 1, 5, 104, 2, 116, 58, 54, 12, 98, 217, 39, 253, 125, 204, 92, 211, 41, 13, 62, 33, 238, 72, 84, 164, 119, 163, 189, 163, 84, 209, 27, 160, 16, 2, 17, 0, 0, 0, 5, 212, 164, 1, 224, 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