Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03db2f75e4b876c3708f90ca9da6d35e53263e0924e89d7c4146a44ed601628a

Tx prefix hash: c80f9f6cdf2860ff4b1200acd6aeca5d9710f9c01d996e963ecb90ed40245a0a
Tx public key: 4452adff40ceb8a345c510c977ae876e438a960f480a59a8feb148c83a4af08a
Timestamp: 1761549291 Timestamp [UCT]: 2025-10-27 07:14:51 Age [y:d:h:m:s]: 00:055:04:27:20
Block: 1398906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39502 RingCT/type: yes/0
Extra: 014452adff40ceb8a345c510c977ae876e438a960f480a59a8feb148c83a4af08a021100000001df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2768a90b60c3fc45cfe434f1bc436596eab1dbbacb9d506aea26d8127ce5e1b4 0.600000000000 1887209 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": 1398916, "vin": [ { "gen": { "height": 1398906 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2768a90b60c3fc45cfe434f1bc436596eab1dbbacb9d506aea26d8127ce5e1b4" } } ], "extra": [ 1, 68, 82, 173, 255, 64, 206, 184, 163, 69, 197, 16, 201, 119, 174, 135, 110, 67, 138, 150, 15, 72, 10, 89, 168, 254, 177, 72, 200, 58, 74, 240, 138, 2, 17, 0, 0, 0, 1, 223, 90, 36, 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