Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cedc718e62497dc6c462963f1144b7ed6f7c6dbd92d80a48400d033532fc49a1

Tx prefix hash: cfa79028c04699cd9f8db49794aea96d977caa12196697a6499674184b860fec
Tx public key: 983de131f1f8cb1a2f2b5442d67fa1c62d86a4b1a9514993c27d20ed2f49bd2d
Timestamp: 1717673155 Timestamp [UCT]: 2024-06-06 11:25:55 Age [y:d:h:m:s]: 00:295:23:28:15
Block: 1038271 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211521 RingCT/type: yes/0
Extra: 01983de131f1f8cb1a2f2b5442d67fa1c62d86a4b1a9514993c27d20ed2f49bd2d0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 917c41c2883b9156a22d7158acdf87c7cf1327f072c2dd14cf2d210bd68f635c 0.600000000000 1506832 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": 1038281, "vin": [ { "gen": { "height": 1038271 } } ], "vout": [ { "amount": 600000000, "target": { "key": "917c41c2883b9156a22d7158acdf87c7cf1327f072c2dd14cf2d210bd68f635c" } } ], "extra": [ 1, 152, 61, 225, 49, 241, 248, 203, 26, 47, 43, 84, 66, 214, 127, 161, 198, 45, 134, 164, 177, 169, 81, 73, 147, 194, 125, 32, 237, 47, 73, 189, 45, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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