Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9fb0801c062e5bea207dc87c3a7fd000c7efcc516c2f96e3198b36fd866221a

Tx prefix hash: e072030fcd2258dcf87a45373b2b0aa5efbbd674e74914ac24c460056ba22fe8
Tx public key: dd8926bdd5ca84f5a76ca35165812be66b6b7ef9b3d2b592442c58c13af58aa7
Timestamp: 1763374096 Timestamp [UCT]: 2025-11-17 10:08:16 Age [y:d:h:m:s]: 00:011:00:58:36
Block: 1414025 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7898 RingCT/type: yes/0
Extra: 01dd8926bdd5ca84f5a76ca35165812be66b6b7ef9b3d2b592442c58c13af58aa702110000000234af31cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a28f7eaf6ac2510ab75cbf34f7aa05a8ce69a73743d0cc112835cb6a96248fa 0.600000000000 1902510 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": 1414035, "vin": [ { "gen": { "height": 1414025 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a28f7eaf6ac2510ab75cbf34f7aa05a8ce69a73743d0cc112835cb6a96248fa" } } ], "extra": [ 1, 221, 137, 38, 189, 213, 202, 132, 245, 167, 108, 163, 81, 101, 129, 43, 230, 107, 107, 126, 249, 179, 210, 181, 146, 68, 44, 88, 193, 58, 245, 138, 167, 2, 17, 0, 0, 0, 2, 52, 175, 49, 204, 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