Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17f704f12f00f76b45090a5e855cbbb963f1ef746939fe2404c84d4e7c49a9e3

Tx prefix hash: 673d477bc1d7f7f184ae4c9e12ac48871cf99e71f9945b43a1d86e7cb6bf65d2
Tx public key: e717ec91397199eb195226705e02d533dceb60951bd72312d06090d3361fb1d9
Timestamp: 1582431327 Timestamp [UCT]: 2020-02-23 04:15:27 Age [y:d:h:m:s]: 04:310:10:10:39
Block: 70509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1114550 RingCT/type: yes/0
Extra: 01e717ec91397199eb195226705e02d533dceb60951bd72312d06090d3361fb1d902110000000103d36d11000000000000000000

1 output(s) for total of 358.405954422000 dcy

stealth address amount amount idx
00: 134f50f0261ded2bdeb1787f97177a6c4cf0cb8b0dc0d7420e25ddda2ae8c696 358.405954422000 130321 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": 70519, "vin": [ { "gen": { "height": 70509 } } ], "vout": [ { "amount": 358405954422, "target": { "key": "134f50f0261ded2bdeb1787f97177a6c4cf0cb8b0dc0d7420e25ddda2ae8c696" } } ], "extra": [ 1, 231, 23, 236, 145, 57, 113, 153, 235, 25, 82, 38, 112, 94, 2, 213, 51, 220, 235, 96, 149, 27, 215, 35, 18, 208, 96, 144, 211, 54, 31, 177, 217, 2, 17, 0, 0, 0, 1, 3, 211, 109, 17, 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