Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0d4d2439466968258ccb82044610a5a02084adb4f3a05128a7de2dae6e14415

Tx prefix hash: a02dca8593e308f31cf035cab08737143d858d48c315e30debed9192012405af
Tx public key: a6fb092de35c587c162223a1f8f0e14d7e2e71e6ebee392ee5fe4b104fbd0a02
Timestamp: 1746555951 Timestamp [UCT]: 2025-05-06 18:25:51 Age [y:d:h:m:s]: 00:197:13:35:38
Block: 1277195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138910 RingCT/type: yes/0
Extra: 01a6fb092de35c587c162223a1f8f0e14d7e2e71e6ebee392ee5fe4b104fbd0a020211000000011f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7874651377da5181d1e9b0aec94c60996fa8a0d3d24f080aa953a9ab1e3222f 0.600000000000 1764548 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": 1277205, "vin": [ { "gen": { "height": 1277195 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7874651377da5181d1e9b0aec94c60996fa8a0d3d24f080aa953a9ab1e3222f" } } ], "extra": [ 1, 166, 251, 9, 45, 227, 92, 88, 124, 22, 34, 35, 161, 248, 240, 225, 77, 126, 46, 113, 230, 235, 238, 57, 46, 229, 254, 75, 16, 79, 189, 10, 2, 2, 17, 0, 0, 0, 1, 31, 144, 81, 122, 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