Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66f38808acf9991714443a8e77cfd2be7ef131f261d10984cf506b60b704fee7

Tx prefix hash: 305c3a6082289d78967f5cc4100baddac1f961e9cf14431ed307e176b31a5999
Tx public key: f828e2dec8aa0471c748e11e357dd60dc7d82848c30c57451f3e7ea4115bbd5f
Timestamp: 1719066494 Timestamp [UCT]: 2024-06-22 14:28:14 Age [y:d:h:m:s]: 00:269:20:58:42
Block: 1049801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192870 RingCT/type: yes/0
Extra: 01f828e2dec8aa0471c748e11e357dd60dc7d82848c30c57451f3e7ea4115bbd5f0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a417b3be939b96196a83b7d75fdfc0fdaab7ec6cfcfe229a11c21270e2515d1b 0.600000000000 1519906 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": 1049811, "vin": [ { "gen": { "height": 1049801 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a417b3be939b96196a83b7d75fdfc0fdaab7ec6cfcfe229a11c21270e2515d1b" } } ], "extra": [ 1, 248, 40, 226, 222, 200, 170, 4, 113, 199, 72, 225, 30, 53, 125, 214, 13, 199, 216, 40, 72, 195, 12, 87, 69, 31, 62, 126, 164, 17, 91, 189, 95, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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