Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14db6f43efc4f0e748e48f7b9b932b51af86b13d544983ef44136884cd7ce689

Tx prefix hash: 6c7afec4d003528a03cc9f0e6a71162c054bf568d1dd2811bd2d854874fd84ba
Tx public key: 59d23a3bf7c5d38a736a484a411541b5cebcd9b48fe6e92e41801092a5e67884
Timestamp: 1726565128 Timestamp [UCT]: 2024-09-17 09:25:28 Age [y:d:h:m:s]: 00:209:23:52:07
Block: 1111978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149920 RingCT/type: yes/0
Extra: 0159d23a3bf7c5d38a736a484a411541b5cebcd9b48fe6e92e41801092a5e6788402110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1bffd01a279283e842aade9da5d30f7db7d1aef5da4ba356471d35c239fc440 0.600000000000 1591131 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": 1111988, "vin": [ { "gen": { "height": 1111978 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1bffd01a279283e842aade9da5d30f7db7d1aef5da4ba356471d35c239fc440" } } ], "extra": [ 1, 89, 210, 58, 59, 247, 197, 211, 138, 115, 106, 72, 74, 65, 21, 65, 181, 206, 188, 217, 180, 143, 230, 233, 46, 65, 128, 16, 146, 165, 230, 120, 132, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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