Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 129e0ad5593e5e9993355cb5bf98b5e940ff889d7563fc95cc2b30e0e8bc1e60

Tx prefix hash: dd2a5727cbf97109ccbfd8cfb43487446414aca785585e4d8c4653dcf0957b7b
Tx public key: 2f87c7c1b7d86f7db4e0a245ed2a5fcd6cc4b3a277b04bd5d8f3abc8613e05f2
Timestamp: 1733127947 Timestamp [UCT]: 2024-12-02 08:25:47 Age [y:d:h:m:s]: 00:115:17:20:56
Block: 1166293 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82511 RingCT/type: yes/0
Extra: 012f87c7c1b7d86f7db4e0a245ed2a5fcd6cc4b3a277b04bd5d8f3abc8613e05f2021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90c5738ab1c0c20c18013d763aab445e8e4cf36ee812594ddc70ed6214f59d02 0.600000000000 1651970 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": 1166303, "vin": [ { "gen": { "height": 1166293 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90c5738ab1c0c20c18013d763aab445e8e4cf36ee812594ddc70ed6214f59d02" } } ], "extra": [ 1, 47, 135, 199, 193, 183, 216, 111, 125, 180, 224, 162, 69, 237, 42, 95, 205, 108, 196, 179, 162, 119, 176, 75, 213, 216, 243, 171, 200, 97, 62, 5, 242, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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