Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8325bd86e0a2111d66d47f668cb3decbc9d17e7fdd084cc8e12d13a1b8715f46

Tx prefix hash: 5a0cd957d70d6a11d868389fcd0793273c1d4fca3be2b48df05ce348ed441821
Tx public key: f260b49c295dacff9b43c91daebc856121a3c33335fe19898b092d7c9002bf42
Timestamp: 1687607123 Timestamp [UCT]: 2023-06-24 11:45:23 Age [y:d:h:m:s]: 01:314:02:34:22
Block: 789260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485667 RingCT/type: yes/0
Extra: 01f260b49c295dacff9b43c91daebc856121a3c33335fe19898b092d7c9002bf4202110000000333af99f4000000000000000000

1 output(s) for total of 1.488860912000 dcy

stealth address amount amount idx
00: fddf233dbd3db29e23ef3c4da1b4bdb6bf508d89aae04fe21d62bd3a3c157ad2 1.488860912000 1239465 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": 789270, "vin": [ { "gen": { "height": 789260 } } ], "vout": [ { "amount": 1488860912, "target": { "key": "fddf233dbd3db29e23ef3c4da1b4bdb6bf508d89aae04fe21d62bd3a3c157ad2" } } ], "extra": [ 1, 242, 96, 180, 156, 41, 93, 172, 255, 155, 67, 201, 29, 174, 188, 133, 97, 33, 163, 195, 51, 53, 254, 25, 137, 139, 9, 45, 124, 144, 2, 191, 66, 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