Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 662109269c590d2566e477666839acb3f57c4f131319734bddb04ff9798cd7cd

Tx prefix hash: 702b23ddd4ba54b149d1b22594fb09c7d44f45c9dcfd350639f450a2e550d4e2
Tx public key: 865f76f3cd88c3a6472d87ad5cb982f0b3a7785335d59e1aeb6546e6df3daf61
Timestamp: 1700258986 Timestamp [UCT]: 2023-11-17 22:09:46 Age [y:d:h:m:s]: 01:143:01:27:16
Block: 893895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363413 RingCT/type: yes/0
Extra: 01865f76f3cd88c3a6472d87ad5cb982f0b3a7785335d59e1aeb6546e6df3daf61021100000002faf35c9c000000000000000000

1 output(s) for total of 0.670123401000 dcy

stealth address amount amount idx
00: 37df9498ff14299803a23349af850b35521c1143193742d0bd83d4e25869ce54 0.670123401000 1350080 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": 893905, "vin": [ { "gen": { "height": 893895 } } ], "vout": [ { "amount": 670123401, "target": { "key": "37df9498ff14299803a23349af850b35521c1143193742d0bd83d4e25869ce54" } } ], "extra": [ 1, 134, 95, 118, 243, 205, 136, 195, 166, 71, 45, 135, 173, 92, 185, 130, 240, 179, 167, 120, 83, 53, 213, 158, 26, 235, 101, 70, 230, 223, 61, 175, 97, 2, 17, 0, 0, 0, 2, 250, 243, 92, 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