Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abec3f0df89bed2c17f5dcead3ec2d230e645ee8c51543b223748b7ed3155c01

Tx prefix hash: 598876916ee0efd507fd7be8e9fc49f22bdef8471b10c800731494da1611689e
Tx public key: 0f1a10dc8c67e6d340923d1ee0f38ecd109d917a64f16e08264bd01aa946c775
Timestamp: 1654723519 Timestamp [UCT]: 2022-06-08 21:25:19 Age [y:d:h:m:s]: 03:145:20:28:30
Block: 518364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 883728 RingCT/type: yes/0
Extra: 010f1a10dc8c67e6d340923d1ee0f38ecd109d917a64f16e08264bd01aa946c77502110000000775e3f0e9000000000000000000

1 output(s) for total of 11.761022031000 dcy

stealth address amount amount idx
00: e7707b637b314fc31ffbb8af53615d3f152f1f958b7dd778704052b721eeb283 11.761022031000 945807 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": 518374, "vin": [ { "gen": { "height": 518364 } } ], "vout": [ { "amount": 11761022031, "target": { "key": "e7707b637b314fc31ffbb8af53615d3f152f1f958b7dd778704052b721eeb283" } } ], "extra": [ 1, 15, 26, 16, 220, 140, 103, 230, 211, 64, 146, 61, 30, 224, 243, 142, 205, 16, 157, 145, 122, 100, 241, 110, 8, 38, 75, 208, 26, 169, 70, 199, 117, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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