Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4432beb1f4332039e3e2a7cae079692400d78ff611c2429326351da600bd1140

Tx prefix hash: c3796cd3bea31278a8e973c7669ccb1dff1f8332d7f6f8f4345a83f8f27012d5
Tx public key: 96e2254e92ddf2d9762f10bcb525de32752466d738fbe4f2a53e12e74e0e96d3
Timestamp: 1764565564 Timestamp [UCT]: 2025-12-01 05:06:04 Age [y:d:h:m:s]: 00:004:06:52:07
Block: 1423900 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3075 RingCT/type: yes/0
Extra: 0196e2254e92ddf2d9762f10bcb525de32752466d738fbe4f2a53e12e74e0e96d302110000000243b50471000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9858d9aa3518917b88fa94d919b6bb64a2b9e1b933aea6dd7ca6fbff25e4bdf9 0.600000000000 1912527 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": 1423910, "vin": [ { "gen": { "height": 1423900 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9858d9aa3518917b88fa94d919b6bb64a2b9e1b933aea6dd7ca6fbff25e4bdf9" } } ], "extra": [ 1, 150, 226, 37, 78, 146, 221, 242, 217, 118, 47, 16, 188, 181, 37, 222, 50, 117, 36, 102, 215, 56, 251, 228, 242, 165, 62, 18, 231, 78, 14, 150, 211, 2, 17, 0, 0, 0, 2, 67, 181, 4, 113, 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