Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad9c822a0b9f53b6b461c1f4577b46d60b3853eeb1704b625397d49ca05d6a3b

Tx prefix hash: 62607c19ebc1fa2b862aaf12ccebd03ba4bf5d446a50c1eca8eda3053b956509
Tx public key: 06460851605e75d7179c756aeef624f1b7d1956031b9be2ecca0ea1cfcedfdc3
Timestamp: 1757680619 Timestamp [UCT]: 2025-09-12 12:36:59 Age [y:d:h:m:s]: 00:100:23:40:43
Block: 1366834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72305 RingCT/type: yes/0
Extra: 0106460851605e75d7179c756aeef624f1b7d1956031b9be2ecca0ea1cfcedfdc3021100000002b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb5f772753f9f7c44741633dede9460d737bfd0fcc962fea6f4f6ad28e4d7279 0.600000000000 1854873 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": 1366844, "vin": [ { "gen": { "height": 1366834 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb5f772753f9f7c44741633dede9460d737bfd0fcc962fea6f4f6ad28e4d7279" } } ], "extra": [ 1, 6, 70, 8, 81, 96, 94, 117, 215, 23, 156, 117, 106, 238, 246, 36, 241, 183, 209, 149, 96, 49, 185, 190, 46, 204, 160, 234, 28, 252, 237, 253, 195, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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