Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f966dbc2e930883b9c54bbdfd2a1efd5a3a4a23757c4d15e6d41b5cf6703ee22

Tx prefix hash: 9a4a4a67eb68813c03d15eb1d77b5b64fb78addd5b74ffb2c4b449cc54200dcd
Tx public key: b06e16df00d2beb643134e3fde0b1a37d0529c1eec7380b15352b09a0b337265
Timestamp: 1680979598 Timestamp [UCT]: 2023-04-08 18:46:38 Age [y:d:h:m:s]: 02:007:07:53:33
Block: 734353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 527340 RingCT/type: yes/0
Extra: 01b06e16df00d2beb643134e3fde0b1a37d0529c1eec7380b15352b09a0b337265021100000007b3164c24000000000000000000

1 output(s) for total of 2.263517688000 dcy

stealth address amount amount idx
00: af0fc47396c6b3dd85810a92289807863ac7308f6a0b7f4864bf1ae9c33bfe4f 2.263517688000 1180544 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": 734363, "vin": [ { "gen": { "height": 734353 } } ], "vout": [ { "amount": 2263517688, "target": { "key": "af0fc47396c6b3dd85810a92289807863ac7308f6a0b7f4864bf1ae9c33bfe4f" } } ], "extra": [ 1, 176, 110, 22, 223, 0, 210, 190, 182, 67, 19, 78, 63, 222, 11, 26, 55, 208, 82, 156, 30, 236, 115, 128, 177, 83, 82, 176, 154, 11, 51, 114, 101, 2, 17, 0, 0, 0, 7, 179, 22, 76, 36, 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