Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e649f16e0bc454419bfab185341bc42ffc0fbaaeceff87ef0103091366850b76

Tx prefix hash: c8b32c40c235cd20bbfce18ec08ec2a82f4eab3cef8d6fcf47d9c68bae5a0aa3
Tx public key: df709699c82fa252f99e254bcae6c63e462a9a5a28782f89c830dc05ed201072
Timestamp: 1715496221 Timestamp [UCT]: 2024-05-12 06:43:41 Age [y:d:h:m:s]: 01:005:14:36:57
Block: 1020245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264898 RingCT/type: yes/0
Extra: 01df709699c82fa252f99e254bcae6c63e462a9a5a28782f89c830dc05ed201072021100000003e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5429fe2661db101e46df365274a38e264c3ba83c31e1d434caaa67cdea4678ba 0.600000000000 1484306 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": 1020255, "vin": [ { "gen": { "height": 1020245 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5429fe2661db101e46df365274a38e264c3ba83c31e1d434caaa67cdea4678ba" } } ], "extra": [ 1, 223, 112, 150, 153, 200, 47, 162, 82, 249, 158, 37, 75, 202, 230, 198, 62, 70, 42, 154, 90, 40, 120, 47, 137, 200, 48, 220, 5, 237, 32, 16, 114, 2, 17, 0, 0, 0, 3, 224, 133, 50, 182, 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