Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 485e963cffabd03fdd7a7e6e84e86e3ef697ac94d350b4623b036fe9d5dbe4d4

Tx prefix hash: b5df06373aa2caf1cd0baf7ce3ab9ef0daa22574c49f263a7cc0af1f6f132bfd
Tx public key: a1658f1f792a8fab09caec5ce97b80b0151ca1412cf0a2ed6159bea7e0e1bd75
Timestamp: 1702251664 Timestamp [UCT]: 2023-12-10 23:41:04 Age [y:d:h:m:s]: 02:012:08:06:48
Block: 910413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 528588 RingCT/type: yes/0
Extra: 01a1658f1f792a8fab09caec5ce97b80b0151ca1412cf0a2ed6159bea7e0e1bd750211000000014b8f5122000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39dea371a9a09d3d379e7750e86ab6a11f82c8b1c93d88d39c4c991df95b0a3f 0.600000000000 1367570 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": 910423, "vin": [ { "gen": { "height": 910413 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39dea371a9a09d3d379e7750e86ab6a11f82c8b1c93d88d39c4c991df95b0a3f" } } ], "extra": [ 1, 161, 101, 143, 31, 121, 42, 143, 171, 9, 202, 236, 92, 233, 123, 128, 176, 21, 28, 161, 65, 44, 240, 162, 237, 97, 89, 190, 167, 224, 225, 189, 117, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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