Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3a7a0d1507c0fd004e2912bd77948a4a8a00fd2aeda1c5a4b8b47b6837afeec

Tx prefix hash: e960a24d2610af402db20fc92e731ff26a5356dc45ae1b7c63244693405a6d41
Tx public key: bcf32904d8503df79a3762994db90b52ccc82ecc507b45d4cd7d9fc675819999
Timestamp: 1737778250 Timestamp [UCT]: 2025-01-25 04:10:50 Age [y:d:h:m:s]: 00:330:21:10:52
Block: 1204745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234081 RingCT/type: yes/0
Extra: 01bcf32904d8503df79a3762994db90b52ccc82ecc507b45d4cd7d9fc6758199990211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4aecc4b9664486619bef86b61666c2a8dc4b7e46339299c7b6bdda2debfc89d 0.600000000000 1691438 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": 1204755, "vin": [ { "gen": { "height": 1204745 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4aecc4b9664486619bef86b61666c2a8dc4b7e46339299c7b6bdda2debfc89d" } } ], "extra": [ 1, 188, 243, 41, 4, 216, 80, 61, 247, 154, 55, 98, 153, 77, 185, 11, 82, 204, 200, 46, 204, 80, 123, 69, 212, 205, 125, 159, 198, 117, 129, 153, 153, 2, 17, 0, 0, 0, 1, 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