Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2d44c255f09e8688fecf4ff3503670221132297e945a8a6b7f3bf5e1a208888

Tx prefix hash: fd31b36d0a33a991da8eb7afb700580f2c1e80e06c6dd46c664c7072dfeecf9d
Tx public key: 1c10cc4188fa754f1b24e2bf753032a9d21520f67545b5ee80b9a7f0d565dc18
Timestamp: 1717816483 Timestamp [UCT]: 2024-06-08 03:14:43 Age [y:d:h:m:s]: 00:287:16:47:25
Block: 1039453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205604 RingCT/type: yes/0
Extra: 011c10cc4188fa754f1b24e2bf753032a9d21520f67545b5ee80b9a7f0d565dc1802110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 853a151ee09728c22bf3da8d3a725029d0a6fd12848ca2418c7bc3011882108c 0.600000000000 1508094 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": 1039463, "vin": [ { "gen": { "height": 1039453 } } ], "vout": [ { "amount": 600000000, "target": { "key": "853a151ee09728c22bf3da8d3a725029d0a6fd12848ca2418c7bc3011882108c" } } ], "extra": [ 1, 28, 16, 204, 65, 136, 250, 117, 79, 27, 36, 226, 191, 117, 48, 50, 169, 210, 21, 32, 246, 117, 69, 181, 238, 128, 185, 167, 240, 213, 101, 220, 24, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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