Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7fecb8f98c7538e3bb667afe55622c5f3cd3d18f3cf3ee118951bc23d64f3789

Tx prefix hash: 4311c9e90b3e371c580e6c76f8538864dcda026b4059abd656dfdace8cbd6911
Tx public key: adb8ec8e53c25f1621037f2739986caa9746aef4d157afc18b1e490f04dce0a1
Timestamp: 1699130554 Timestamp [UCT]: 2023-11-04 20:42:34 Age [y:d:h:m:s]: 01:145:03:27:23
Block: 884788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364681 RingCT/type: yes/0
Extra: 01adb8ec8e53c25f1621037f2739986caa9746aef4d157afc18b1e490f04dce0a1021100000001faf35c9c000000000000000000

1 output(s) for total of 0.718340030000 dcy

stealth address amount amount idx
00: 709598de96d0f4d5e37aa3c3cb1a6384396491fdbab709e5d3b4dcad147eeb12 0.718340030000 1340535 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": 884798, "vin": [ { "gen": { "height": 884788 } } ], "vout": [ { "amount": 718340030, "target": { "key": "709598de96d0f4d5e37aa3c3cb1a6384396491fdbab709e5d3b4dcad147eeb12" } } ], "extra": [ 1, 173, 184, 236, 142, 83, 194, 95, 22, 33, 3, 127, 39, 57, 152, 108, 170, 151, 70, 174, 244, 209, 87, 175, 193, 139, 30, 73, 15, 4, 220, 224, 161, 2, 17, 0, 0, 0, 1, 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