Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0516ad300a2ce1f1a4cf2bec353fda7934ab328e2cb8d5c81240fa5c49ccf55

Tx prefix hash: 355abf1400a83e70ee875dbb17a973c0faa3e9da8c7396e4134d41c2602948ca
Tx public key: d3efd7f9773a48cc6de918611b0582e331ebc3b21acbbb7be0d7e6f0a8b72a48
Timestamp: 1581946361 Timestamp [UCT]: 2020-02-17 13:32:41 Age [y:d:h:m:s]: 05:261:15:15:03
Block: 66651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1337905 RingCT/type: yes/0
Extra: 01d3efd7f9773a48cc6de918611b0582e331ebc3b21acbbb7be0d7e6f0a8b72a48021100000001724f989b000000000000000000

1 output(s) for total of 369.135340948000 dcy

stealth address amount amount idx
00: 4b307a1cbf8c6d2be376da3eb86eda62f7c6395cf8e403c61073a3d236c6e1ef 369.135340948000 122800 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": 66661, "vin": [ { "gen": { "height": 66651 } } ], "vout": [ { "amount": 369135340948, "target": { "key": "4b307a1cbf8c6d2be376da3eb86eda62f7c6395cf8e403c61073a3d236c6e1ef" } } ], "extra": [ 1, 211, 239, 215, 249, 119, 58, 72, 204, 109, 233, 24, 97, 27, 5, 130, 227, 49, 235, 195, 178, 26, 203, 187, 123, 224, 215, 230, 240, 168, 183, 42, 72, 2, 17, 0, 0, 0, 1, 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