Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88f7c17e91f2b95f666c7a4210d6e233016287bc4700b7d368d560ee5bc51106

Tx prefix hash: 12308b5c6a936bd4d78baa6798cfb412b51df79e3439e47dea406d95c88df71e
Tx public key: d3f19ca2d43a160f2015f5563e36a8a31627f237ac91f20f1e86006c1e29753e
Timestamp: 1728726227 Timestamp [UCT]: 2024-10-12 09:43:47 Age [y:d:h:m:s]: 00:043:02:25:40
Block: 1129905 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30763 RingCT/type: yes/0
Extra: 01d3f19ca2d43a160f2015f5563e36a8a31627f237ac91f20f1e86006c1e29753e02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 390d5e418f8a8402b54bcd7798bdf35b7a5716de6db3378b0b0923be77920d34 0.600000000000 1612776 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": 1129915, "vin": [ { "gen": { "height": 1129905 } } ], "vout": [ { "amount": 600000000, "target": { "key": "390d5e418f8a8402b54bcd7798bdf35b7a5716de6db3378b0b0923be77920d34" } } ], "extra": [ 1, 211, 241, 156, 162, 212, 58, 22, 15, 32, 21, 245, 86, 62, 54, 168, 163, 22, 39, 242, 55, 172, 145, 242, 15, 30, 134, 0, 108, 30, 41, 117, 62, 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