Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e600a856811779468799dea86952a3a9f00b2a013fe89e1a4d4ecc7526f98e0

Tx prefix hash: 246a4cbf0470e652a43b1a792f743f3c6a3a5de5034c1d0a178be13f4f56978d
Tx public key: ad6e03ecfe4b26ab7455738d167faf4fb91ef07f7db21069af46cf40a2c185e8
Timestamp: 1741115511 Timestamp [UCT]: 2025-03-04 19:11:51 Age [y:d:h:m:s]: 00:261:23:16:35
Block: 1232155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184974 RingCT/type: yes/0
Extra: 01ad6e03ecfe4b26ab7455738d167faf4fb91ef07f7db21069af46cf40a2c185e80211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1edc1196fd0621c55b867d6cc2c5ed7d3d4a05e85de764d657f4fa7d0d454a13 0.600000000000 1719068 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": 1232165, "vin": [ { "gen": { "height": 1232155 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1edc1196fd0621c55b867d6cc2c5ed7d3d4a05e85de764d657f4fa7d0d454a13" } } ], "extra": [ 1, 173, 110, 3, 236, 254, 75, 38, 171, 116, 85, 115, 141, 22, 127, 175, 79, 185, 30, 240, 127, 125, 178, 16, 105, 175, 70, 207, 64, 162, 193, 133, 232, 2, 17, 0, 0, 0, 6, 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