Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8283e7649836adef9a715b96495cca45f6633be28d5fae57756c96624d5a1475

Tx prefix hash: 465e0caa368e38f209de3707ff9117e4af33364893215f00572d6c5e30a6902f
Tx public key: be633a4df96d53c8fa9e9e4852d8f0d236d101815b5ecdb0316adeede66d0ce8
Timestamp: 1701250405 Timestamp [UCT]: 2023-11-29 09:33:25 Age [y:d:h:m:s]: 01:141:05:09:13
Block: 902110 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362101 RingCT/type: yes/0
Extra: 01be633a4df96d53c8fa9e9e4852d8f0d236d101815b5ecdb0316adeede66d0ce80211000000024b8f5122000000000000000000

1 output(s) for total of 0.629412069000 dcy

stealth address amount amount idx
00: 1dc686dcf3ae4d6469d14b5250c417cd0abdf320ca88e4bb3d25226182fd2102 0.629412069000 1358723 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": 902120, "vin": [ { "gen": { "height": 902110 } } ], "vout": [ { "amount": 629412069, "target": { "key": "1dc686dcf3ae4d6469d14b5250c417cd0abdf320ca88e4bb3d25226182fd2102" } } ], "extra": [ 1, 190, 99, 58, 77, 249, 109, 83, 200, 250, 158, 158, 72, 82, 216, 240, 210, 54, 209, 1, 129, 91, 94, 205, 176, 49, 106, 222, 237, 230, 109, 12, 232, 2, 17, 0, 0, 0, 2, 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