Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 687aebbb6585ef835b6ca5f037a3a597a013f87fb1ae2edebfe65ba76c9f36f2

Tx prefix hash: 82235671f059b1cce5858ca4700615ce2f11d43890ddb151e0ff34fcb6a4da18
Tx public key: 1fcc91d639371ac5a7c49d242407e674508a2f4a97a13cae7ec193c04387475e
Timestamp: 1696041564 Timestamp [UCT]: 2023-09-30 02:39:24 Age [y:d:h:m:s]: 01:048:00:44:41
Block: 859126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295575 RingCT/type: yes/0
Extra: 011fcc91d639371ac5a7c49d242407e674508a2f4a97a13cae7ec193c04387475e0211000000094b8f5122000000000000000000

1 output(s) for total of 0.873693219000 dcy

stealth address amount amount idx
00: 56a9a81b845243671f8a701cc293a34fd0856bd25358e73dca5bb1abec98fa0a 0.873693219000 1313336 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": 859136, "vin": [ { "gen": { "height": 859126 } } ], "vout": [ { "amount": 873693219, "target": { "key": "56a9a81b845243671f8a701cc293a34fd0856bd25358e73dca5bb1abec98fa0a" } } ], "extra": [ 1, 31, 204, 145, 214, 57, 55, 26, 197, 167, 196, 157, 36, 36, 7, 230, 116, 80, 138, 47, 74, 151, 161, 60, 174, 126, 193, 147, 192, 67, 135, 71, 94, 2, 17, 0, 0, 0, 9, 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