Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a71ff17be12ab2075a7475a498e0657fdf9db65be37b320abee015c97633530c

Tx prefix hash: dc43f9b8d214232385fd0c299d5a57b12ca750c8097c4bb45edbd0583a9c5b5d
Tx public key: db11768321f1a7ff9b37e5dccfbc133657a6f01d189e463922d00a1e1cbc0c8c
Timestamp: 1726560379 Timestamp [UCT]: 2024-09-17 08:06:19 Age [y:d:h:m:s]: 01:053:15:49:05
Block: 1111946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296764 RingCT/type: yes/0
Extra: 01db11768321f1a7ff9b37e5dccfbc133657a6f01d189e463922d00a1e1cbc0c8c021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 786858ddaf30e88a4d94328ec3a287586a8f56e20a39558de8abd91e799e466e 0.600000000000 1591087 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": 1111956, "vin": [ { "gen": { "height": 1111946 } } ], "vout": [ { "amount": 600000000, "target": { "key": "786858ddaf30e88a4d94328ec3a287586a8f56e20a39558de8abd91e799e466e" } } ], "extra": [ 1, 219, 17, 118, 131, 33, 241, 167, 255, 155, 55, 229, 220, 207, 188, 19, 54, 87, 166, 240, 29, 24, 158, 70, 57, 34, 208, 10, 30, 28, 188, 12, 140, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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