Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9498dbbe686ce22fd123210f44dd0eaf879e52b90acf2102efb6ef40c723e039

Tx prefix hash: e509853473f7e288080807c3f9c19f425113c3e491516b51f5a4f839281328f3
Tx public key: 2cae2f2e668f424492813cf956e233a191dbe23f31fa0bc4cd17aae3da6cff8d
Timestamp: 1751326907 Timestamp [UCT]: 2025-06-30 23:41:47 Age [y:d:h:m:s]: 00:142:08:19:42
Block: 1316176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99929 RingCT/type: yes/0
Extra: 012cae2f2e668f424492813cf956e233a191dbe23f31fa0bc4cd17aae3da6cff8d021100000003d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55f96a899903735467640e3295b8f5d7788c748a566d8543940d9de2b08d4b48 0.600000000000 1803833 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": 1316186, "vin": [ { "gen": { "height": 1316176 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55f96a899903735467640e3295b8f5d7788c748a566d8543940d9de2b08d4b48" } } ], "extra": [ 1, 44, 174, 47, 46, 102, 143, 66, 68, 146, 129, 60, 249, 86, 226, 51, 161, 145, 219, 226, 63, 49, 250, 11, 196, 205, 23, 170, 227, 218, 108, 255, 141, 2, 17, 0, 0, 0, 3, 216, 231, 210, 65, 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