Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3581a59411a276caaa44f357abeec23240da90f7e5ad56ae52a75d835327de80

Tx prefix hash: b262ad4306fa6e3e522e0780f7c989f0eb654638c2f1c3b6638d6c13fd086256
Tx public key: 558112ab9a0465fb65366f7a2d3ac622b907fff5f3af0a400c9307a5cf8aba0a
Timestamp: 1705732354 Timestamp [UCT]: 2024-01-20 06:32:34 Age [y:d:h:m:s]: 01:008:19:24:37
Block: 939236 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267389 RingCT/type: yes/0
Extra: 01558112ab9a0465fb65366f7a2d3ac622b907fff5f3af0a400c9307a5cf8aba0a0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff18f9d17995a79f8be7e179ad204619eda71c6fa174da4fd69ccd30423ae07e 0.600000000000 1397326 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": 939246, "vin": [ { "gen": { "height": 939236 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff18f9d17995a79f8be7e179ad204619eda71c6fa174da4fd69ccd30423ae07e" } } ], "extra": [ 1, 85, 129, 18, 171, 154, 4, 101, 251, 101, 54, 111, 122, 45, 58, 198, 34, 185, 7, 255, 245, 243, 175, 10, 64, 12, 147, 7, 165, 207, 138, 186, 10, 2, 17, 0, 0, 0, 1, 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