Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73370aa97428787fe21f31de743340824516b8ecd779a10b226a4aeca1a06b15

Tx prefix hash: d2a3555b763fa6baa0ac4806d82b7255adff8ae281fccd0479aff7695c1d3475
Tx public key: 8a81bc3af5614d2dcadde5aafc6fce62a0b1dc8fa58d02f98c59f022e7a5a0e2
Timestamp: 1633604690 Timestamp [UCT]: 2021-10-07 11:04:50 Age [y:d:h:m:s]: 03:119:16:44:23
Block: 348434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 862506 RingCT/type: yes/0
Extra: 018a81bc3af5614d2dcadde5aafc6fce62a0b1dc8fa58d02f98c59f022e7a5a0e2021100000011f29d7abf000000000000000000

1 output(s) for total of 43.002523454000 dcy

stealth address amount amount idx
00: a929fe42a7aaf2f95746e2c6a34f4051d8e7a0a1fbe18a7ca3593f9523efe751 43.002523454000 713538 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": 348444, "vin": [ { "gen": { "height": 348434 } } ], "vout": [ { "amount": 43002523454, "target": { "key": "a929fe42a7aaf2f95746e2c6a34f4051d8e7a0a1fbe18a7ca3593f9523efe751" } } ], "extra": [ 1, 138, 129, 188, 58, 245, 97, 77, 45, 202, 221, 229, 170, 252, 111, 206, 98, 160, 177, 220, 143, 165, 141, 2, 249, 140, 89, 240, 34, 231, 165, 160, 226, 2, 17, 0, 0, 0, 17, 242, 157, 122, 191, 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