Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 644d9f7748d191f1465b58ec7e23181d4ec1e6e9e7cbcd5717afa3292b469ee9

Tx prefix hash: 0e3055ea4ca4c11888f86030c66a9a7e67393b5f9b765b99a353feace4d71a1d
Tx public key: 76b1f3deb072aa500576bd6f5ead470e80c1b5c967d586d6088e93efed9e1515
Timestamp: 1734109883 Timestamp [UCT]: 2024-12-13 17:11:23 Age [y:d:h:m:s]: 00:191:21:38:55
Block: 1174450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136744 RingCT/type: yes/0
Extra: 0176b1f3deb072aa500576bd6f5ead470e80c1b5c967d586d6088e93efed9e1515021100000001e890f369000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3e5ef5a746cb19a6fa2c9c139a489bfcaa5b0af62c6d9dbd23e4bca6c99dc60 0.600000000000 1660603 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": 1174460, "vin": [ { "gen": { "height": 1174450 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3e5ef5a746cb19a6fa2c9c139a489bfcaa5b0af62c6d9dbd23e4bca6c99dc60" } } ], "extra": [ 1, 118, 177, 243, 222, 176, 114, 170, 80, 5, 118, 189, 111, 94, 173, 71, 14, 128, 193, 181, 201, 103, 213, 134, 214, 8, 142, 147, 239, 237, 158, 21, 21, 2, 17, 0, 0, 0, 1, 232, 144, 243, 105, 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