Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c859122067b4be696e73ac1c3acd69959c26621c03b2352124447fdfec5fd60c

Tx prefix hash: 02041f73264b1dc3f0a75f2148d0e5c91aa9f751bc512d26f3699ce517af434d
Tx public key: 775ef8da81af3d8a445c4626982f71083fc34743974112a4fb8df8957503900b
Timestamp: 1691026983 Timestamp [UCT]: 2023-08-03 01:43:03 Age [y:d:h:m:s]: 01:181:16:32:52
Block: 817618 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390908 RingCT/type: yes/0
Extra: 01775ef8da81af3d8a445c4626982f71083fc34743974112a4fb8df8957503900b021100000005e6d27f9c000000000000000000

1 output(s) for total of 1.199201770000 dcy

stealth address amount amount idx
00: 0d8a4c22134f463103db6589a6d3cb0affa5219640f21d7fae0c19cc059e02b6 1.199201770000 1269526 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": 817628, "vin": [ { "gen": { "height": 817618 } } ], "vout": [ { "amount": 1199201770, "target": { "key": "0d8a4c22134f463103db6589a6d3cb0affa5219640f21d7fae0c19cc059e02b6" } } ], "extra": [ 1, 119, 94, 248, 218, 129, 175, 61, 138, 68, 92, 70, 38, 152, 47, 113, 8, 63, 195, 71, 67, 151, 65, 18, 164, 251, 141, 248, 149, 117, 3, 144, 11, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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