Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d0b9bf1f2e14ed4170ddd773fef2dd10d39bfc7fd36b54880e4728abe45fb7c

Tx prefix hash: ee4177670bcfafe57e1c32c8d697bd355616e1d994b584742b9f112bd29f92ee
Tx public key: edf944f810d3e6c98e263f1c99fb7e9ddd7cbdae5323eb234810071b443c7ec5
Timestamp: 1582127674 Timestamp [UCT]: 2020-02-19 15:54:34 Age [y:d:h:m:s]: 05:081:17:27:24
Block: 68241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1211540 RingCT/type: yes/0
Extra: 01edf944f810d3e6c98e263f1c99fb7e9ddd7cbdae5323eb234810071b443c7ec5021100000002724f989b000000000000000000

1 output(s) for total of 364.661609998000 dcy

stealth address amount amount idx
00: cff2f396aefe9da79d2ff30afc37a79f425f122c68d5fd7b33ab0b77adfc7e91 364.661609998000 125753 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": 68251, "vin": [ { "gen": { "height": 68241 } } ], "vout": [ { "amount": 364661609998, "target": { "key": "cff2f396aefe9da79d2ff30afc37a79f425f122c68d5fd7b33ab0b77adfc7e91" } } ], "extra": [ 1, 237, 249, 68, 248, 16, 211, 230, 201, 142, 38, 63, 28, 153, 251, 126, 157, 221, 124, 189, 174, 83, 35, 235, 35, 72, 16, 7, 27, 68, 60, 126, 197, 2, 17, 0, 0, 0, 2, 114, 79, 152, 155, 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