Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc7a17b542601d3ede9965ac4887753e58ab59d8f3247c350f42664285de783a

Tx prefix hash: b7f06b73222d1fe90ecf1f0bf67a4e616e852556012334308af53d81608eaa2b
Tx public key: a001fdbd2a88b7d58173fa5684e5feb4b5a217bc3e2ad57b184d2d175c3153d0
Timestamp: 1700438541 Timestamp [UCT]: 2023-11-20 00:02:21 Age [y:d:h:m:s]: 01:006:18:23:53
Block: 895381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266195 RingCT/type: yes/0
Extra: 01a001fdbd2a88b7d58173fa5684e5feb4b5a217bc3e2ad57b184d2d175c3153d002110000000333af99f4000000000000000000

1 output(s) for total of 0.662568900000 dcy

stealth address amount amount idx
00: d9d09d3ddf7ffa26ce6d56eea62da567dc866c94175bec1f47a8f895f2986e8e 0.662568900000 1351614 of 0

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": 895391, "vin": [ { "gen": { "height": 895381 } } ], "vout": [ { "amount": 662568900, "target": { "key": "d9d09d3ddf7ffa26ce6d56eea62da567dc866c94175bec1f47a8f895f2986e8e" } } ], "extra": [ 1, 160, 1, 253, 189, 42, 136, 183, 213, 129, 115, 250, 86, 132, 229, 254, 180, 181, 162, 23, 188, 62, 42, 213, 123, 24, 77, 45, 23, 92, 49, 83, 208, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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