Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ca3814ada23f9621dda113f70ea916bf7c5c5641ea9c24b865a364bbd7d1690

Tx prefix hash: e96af28f20ab8c929f22e7a7cbf13bc92f66c8e3ced71a796a45b287b52efb9c
Tx public key: da607ac66894fcb9571224129e6394476c2a4b2db2ba0473237180fcf4786b9f
Timestamp: 1699353117 Timestamp [UCT]: 2023-11-07 10:31:57 Age [y:d:h:m:s]: 01:008:19:21:44
Block: 886386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267658 RingCT/type: yes/0
Extra: 01da607ac66894fcb9571224129e6394476c2a4b2db2ba0473237180fcf4786b9f02110000000875e3f0e9000000000000000000

1 output(s) for total of 0.709635330000 dcy

stealth address amount amount idx
00: d331f914442156b8248b1e684bbcbcd48573e869d057533d95e3d9b6ca69a46a 0.709635330000 1342201 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": 886396, "vin": [ { "gen": { "height": 886386 } } ], "vout": [ { "amount": 709635330, "target": { "key": "d331f914442156b8248b1e684bbcbcd48573e869d057533d95e3d9b6ca69a46a" } } ], "extra": [ 1, 218, 96, 122, 198, 104, 148, 252, 185, 87, 18, 36, 18, 158, 99, 148, 71, 108, 42, 75, 45, 178, 186, 4, 115, 35, 113, 128, 252, 244, 120, 107, 159, 2, 17, 0, 0, 0, 8, 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