Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9121c02c10b00fcbd948d9c51c41d91226a3bb519893aa3001b9223902ab859c

Tx prefix hash: 3b02d4e74d444438bed2b746d32dbde34295517c1cc189f6f744741bc5559a13
Tx public key: a3ee45f08261d2449c1fdced3a94a1360cc4cb607ce983a6ab1e355e5643ebff
Timestamp: 1749884282 Timestamp [UCT]: 2025-06-14 06:58:02 Age [y:d:h:m:s]: 00:157:06:07:24
Block: 1304673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110146 RingCT/type: yes/0
Extra: 01a3ee45f08261d2449c1fdced3a94a1360cc4cb607ce983a6ab1e355e5643ebff021100000007bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6e1bd6a447807b8f7b51688ad4dc1b7d02f10c3cd7ac9ec45f75121113f9f02 0.600000000000 1792264 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": 1304683, "vin": [ { "gen": { "height": 1304673 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6e1bd6a447807b8f7b51688ad4dc1b7d02f10c3cd7ac9ec45f75121113f9f02" } } ], "extra": [ 1, 163, 238, 69, 240, 130, 97, 210, 68, 156, 31, 220, 237, 58, 148, 161, 54, 12, 196, 203, 96, 124, 233, 131, 166, 171, 30, 53, 94, 86, 67, 235, 255, 2, 17, 0, 0, 0, 7, 191, 81, 178, 162, 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