Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df6d8ed09009c17c4922826d56e46bc1b16a16aa5bbd2cc71a459c0b92050288

Tx prefix hash: 122252e9932b24e2e5622ef57edd9d00b65b6f5afdd54bd916f4356ae1cc67f4
Tx public key: be8f38582ea854d656d71e207a43853a20c3b076a89dd6a87498378070190f1e
Timestamp: 1584523317 Timestamp [UCT]: 2020-03-18 09:21:57 Age [y:d:h:m:s]: 04:286:04:44:34
Block: 84841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1100209 RingCT/type: yes/0
Extra: 01be8f38582ea854d656d71e207a43853a20c3b076a89dd6a87498378070190f1e021100000001e5e30634000000000000000000

1 output(s) for total of 321.282692458000 dcy

stealth address amount amount idx
00: b64fb84b2b384476c17180cff3d83147bda5960d2edcd620aac1d650570bde5e 321.282692458000 153583 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": 84851, "vin": [ { "gen": { "height": 84841 } } ], "vout": [ { "amount": 321282692458, "target": { "key": "b64fb84b2b384476c17180cff3d83147bda5960d2edcd620aac1d650570bde5e" } } ], "extra": [ 1, 190, 143, 56, 88, 46, 168, 84, 214, 86, 215, 30, 32, 122, 67, 133, 58, 32, 195, 176, 118, 168, 157, 214, 168, 116, 152, 55, 128, 112, 25, 15, 30, 2, 17, 0, 0, 0, 1, 229, 227, 6, 52, 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