Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8ea482961d43276c20a278852c3edab5a1859d16cf409c01ae6e42094fcce79

Tx prefix hash: 81b67c220eccc099fac7aed06f8fc11121d64ca8abfb5a6867a7969d51e10156
Tx public key: f17b723624cb5ec268af87c45c3186a9aa729dcc098dd2c497b010e296b45aef
Timestamp: 1725059766 Timestamp [UCT]: 2024-08-30 23:16:06 Age [y:d:h:m:s]: 00:289:15:46:25
Block: 1099499 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206816 RingCT/type: yes/0
Extra: 01f17b723624cb5ec268af87c45c3186a9aa729dcc098dd2c497b010e296b45aef02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94984178d328bcae7e40b9d9d4567a54488f32f269988d585f1b75b05f76ba23 0.600000000000 1575462 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": 1099509, "vin": [ { "gen": { "height": 1099499 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94984178d328bcae7e40b9d9d4567a54488f32f269988d585f1b75b05f76ba23" } } ], "extra": [ 1, 241, 123, 114, 54, 36, 203, 94, 194, 104, 175, 135, 196, 92, 49, 134, 169, 170, 114, 157, 204, 9, 141, 210, 196, 151, 176, 16, 226, 150, 180, 90, 239, 2, 17, 0, 0, 0, 2, 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