Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7995d652a1c22355a4ddd38f9ae8ec487432a79e26788afe24e0f90f2f061742

Tx prefix hash: 760cfc1fa3012d1065bd0c40d7e511b266f6436fa9c443d4e2ca323ac2777b71
Tx public key: e05813680835d425528f11bc64c3356803a8ad8f40fd76609b96575b8345b076
Timestamp: 1722044733 Timestamp [UCT]: 2024-07-27 01:45:33 Age [y:d:h:m:s]: 00:251:00:01:04
Block: 1074500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179294 RingCT/type: yes/0
Extra: 01e05813680835d425528f11bc64c3356803a8ad8f40fd76609b96575b8345b07602110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25b61f3da0256f5132656e97853ff6a5ee9707ad1d1724f1e0c8f9e5d6a1a3e0 0.600000000000 1547013 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": 1074510, "vin": [ { "gen": { "height": 1074500 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25b61f3da0256f5132656e97853ff6a5ee9707ad1d1724f1e0c8f9e5d6a1a3e0" } } ], "extra": [ 1, 224, 88, 19, 104, 8, 53, 212, 37, 82, 143, 17, 188, 100, 195, 53, 104, 3, 168, 173, 143, 64, 253, 118, 96, 155, 150, 87, 91, 131, 69, 176, 118, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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