Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d40bc8ec281dd150730f1854d1abf1f81ddeaa7630bce8a0a507bbec1e678bc6

Tx prefix hash: 77fd3df0a398d7ef09312851d1e592836df8b1337b477d9b221694857d80acd2
Tx public key: 64f911b560acb94687db5a7a305278299634c28a1c2550c9284817dacb97a51e
Timestamp: 1702228885 Timestamp [UCT]: 2023-12-10 17:21:25 Age [y:d:h:m:s]: 01:158:13:47:36
Block: 910221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374508 RingCT/type: yes/0
Extra: 0164f911b560acb94687db5a7a305278299634c28a1c2550c9284817dacb97a51e02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f18c10145b511e6b7bc7cb23f3a58052b30bcd6b9fa1e39747c5c3c338972ef 0.600000000000 1367366 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": 910231, "vin": [ { "gen": { "height": 910221 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f18c10145b511e6b7bc7cb23f3a58052b30bcd6b9fa1e39747c5c3c338972ef" } } ], "extra": [ 1, 100, 249, 17, 181, 96, 172, 185, 70, 135, 219, 90, 122, 48, 82, 120, 41, 150, 52, 194, 138, 28, 37, 80, 201, 40, 72, 23, 218, 203, 151, 165, 30, 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