Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a11b92848aa62a45d61d31d106f1f306e01801d90aa5372007e9b12439cb0ab

Tx prefix hash: db2aef69a34267129c7f2a364b0e161b206b5076f07f5540a0af82826561f8fc
Tx public key: e89b0ffef1bc40216d130de6cbd028b836a7ba4bf4db90a9f9e8d4dde85eb3bb
Timestamp: 1762614843 Timestamp [UCT]: 2025-11-08 15:14:03 Age [y:d:h:m:s]: 00:045:13:24:01
Block: 1407730 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32610 RingCT/type: yes/0
Extra: 01e89b0ffef1bc40216d130de6cbd028b836a7ba4bf4db90a9f9e8d4dde85eb3bb021100000007d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9c91171161ab05f1ec74439e1d5b6bbdf82f368e9d91cde83bcdafbbb5951e0 0.600000000000 1896151 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": 1407740, "vin": [ { "gen": { "height": 1407730 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9c91171161ab05f1ec74439e1d5b6bbdf82f368e9d91cde83bcdafbbb5951e0" } } ], "extra": [ 1, 232, 155, 15, 254, 241, 188, 64, 33, 109, 19, 13, 230, 203, 208, 40, 184, 54, 167, 186, 75, 244, 219, 144, 169, 249, 232, 212, 221, 232, 94, 179, 187, 2, 17, 0, 0, 0, 7, 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