Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db85fdf255fb7b6a602e6afbf05610bf0564b7190b2c50680d1dea88a8628436

Tx prefix hash: d28e9d0f1f0b885ece04671347a10d55076320513fcb1b9c15fcedd901a12b35
Tx public key: 1d0a622a459215fa1abfec62232d492c2504ff1f2278b61d1707f7f4a3f72c0b
Timestamp: 1736864431 Timestamp [UCT]: 2025-01-14 14:20:31 Age [y:d:h:m:s]: 00:307:18:58:33
Block: 1197229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217485 RingCT/type: yes/0
Extra: 011d0a622a459215fa1abfec62232d492c2504ff1f2278b61d1707f7f4a3f72c0b0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0aeb5dd9deb44bd9800f3c09327ddd2c7780a972a937247a1e9ac36e3977fa8d 0.600000000000 1683836 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": 1197239, "vin": [ { "gen": { "height": 1197229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0aeb5dd9deb44bd9800f3c09327ddd2c7780a972a937247a1e9ac36e3977fa8d" } } ], "extra": [ 1, 29, 10, 98, 42, 69, 146, 21, 250, 26, 191, 236, 98, 35, 45, 73, 44, 37, 4, 255, 31, 34, 120, 182, 29, 23, 7, 247, 244, 163, 247, 44, 11, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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