Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d5c583bdb93b2d169d5e8c9617fbd394fb7a39e49f415227297a833e5ac7f6a

Tx prefix hash: d792446db7716c9a15044f48a020b5c83a2cd704d4975c553791659b4625f16e
Tx public key: db1b6616ff3ce477c36cb59f8781794c08055f0fa167b7e7d4b99274185dfabc
Timestamp: 1762159616 Timestamp [UCT]: 2025-11-03 08:46:56 Age [y:d:h:m:s]: 00:016:05:27:55
Block: 1403949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11622 RingCT/type: yes/0
Extra: 01db1b6616ff3ce477c36cb59f8781794c08055f0fa167b7e7d4b99274185dfabc02110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c963f4cc802a31fb95780dfd870dbc2c5a0a915dac2c5e90cb7fb3e1887676c9 0.600000000000 1892304 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": 1403959, "vin": [ { "gen": { "height": 1403949 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c963f4cc802a31fb95780dfd870dbc2c5a0a915dac2c5e90cb7fb3e1887676c9" } } ], "extra": [ 1, 219, 27, 102, 22, 255, 60, 228, 119, 195, 108, 181, 159, 135, 129, 121, 76, 8, 5, 95, 15, 161, 103, 183, 231, 212, 185, 146, 116, 24, 93, 250, 188, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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