Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f728c5286855ca551f4e3d15c5becdea305d409e679904021f493b4d0ff99e2

Tx prefix hash: 76564b763d1a996738a9433174d49e5c8b991b2e0fd963cf01c954030e6518c6
Tx public key: 1f509f84cd725f6ee9b4c28fa0a15602648d8e65787ccda928fedaf0f9b76c51
Timestamp: 1721242035 Timestamp [UCT]: 2024-07-17 18:47:15 Age [y:d:h:m:s]: 00:129:09:07:06
Block: 1067865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92566 RingCT/type: yes/0
Extra: 011f509f84cd725f6ee9b4c28fa0a15602648d8e65787ccda928fedaf0f9b76c5102110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f22d05773e3399d8970a93bb8fab6cc9a153f2064d8d7489cdb18a3a823d6831 0.600000000000 1538796 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": 1067875, "vin": [ { "gen": { "height": 1067865 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f22d05773e3399d8970a93bb8fab6cc9a153f2064d8d7489cdb18a3a823d6831" } } ], "extra": [ 1, 31, 80, 159, 132, 205, 114, 95, 110, 233, 180, 194, 143, 160, 161, 86, 2, 100, 141, 142, 101, 120, 124, 205, 169, 40, 254, 218, 240, 249, 183, 108, 81, 2, 17, 0, 0, 0, 3, 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