Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7efdacd49a18ac486c9887518c4977bbc2cb57cfc0aadefc4a53ce9fdbf5aca

Tx prefix hash: a2b23668fdb9df9c0bf93c7fd4b0309996a2091aab2769431aa962e5b71a240c
Tx public key: 0d3151b8116e38148a2a43face13de10c218b5f5cc90ea29d077ba0956289fd8
Timestamp: 1762364258 Timestamp [UCT]: 2025-11-05 17:37:38 Age [y:d:h:m:s]: 00:048:08:45:20
Block: 1405645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34625 RingCT/type: yes/0
Extra: 010d3151b8116e38148a2a43face13de10c218b5f5cc90ea29d077ba0956289fd80211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b3f5779f30edcd5fa8c21d2cfffa95a9f713f6b192d064b69c2f56094579b80 0.600000000000 1894026 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": 1405655, "vin": [ { "gen": { "height": 1405645 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b3f5779f30edcd5fa8c21d2cfffa95a9f713f6b192d064b69c2f56094579b80" } } ], "extra": [ 1, 13, 49, 81, 184, 17, 110, 56, 20, 138, 42, 67, 250, 206, 19, 222, 16, 194, 24, 181, 245, 204, 144, 234, 41, 208, 119, 186, 9, 86, 40, 159, 216, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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