Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9f34cec1937b8561de013aad9f1f677986a3349edd1caeb80a0d791b78ec140

Tx prefix hash: 4e1980f7f7a5afc31c09ce48a93f3cb12c67e536c3b1a69a45e95bce22171283
Tx public key: 64af58e241e7b8cbccb1eda3bde55a6dec2f2c0090509f65fd20965d91dbd7f0
Timestamp: 1702904645 Timestamp [UCT]: 2023-12-18 13:04:05 Age [y:d:h:m:s]: 01:113:14:18:13
Block: 915826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342321 RingCT/type: yes/0
Extra: 0164af58e241e7b8cbccb1eda3bde55a6dec2f2c0090509f65fd20965d91dbd7f002110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bedb5ba50787431a32a5b4bfc0eabb2be7c656eeafd3921f8012efb8ab492362 0.600000000000 1373260 of 15

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": 915836, "vin": [ { "gen": { "height": 915826 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bedb5ba50787431a32a5b4bfc0eabb2be7c656eeafd3921f8012efb8ab492362" } } ], "extra": [ 1, 100, 175, 88, 226, 65, 231, 184, 203, 204, 177, 237, 163, 189, 229, 90, 109, 236, 47, 44, 0, 144, 80, 159, 101, 253, 32, 150, 93, 145, 219, 215, 240, 2, 17, 0, 0, 0, 4, 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