Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3076c5943cd1c1445473d0ff094caafee9ed0e0e69a16760fd4ab1b253211b48

Tx prefix hash: 11faaa265885a328c7411a209c3c4bd59fbdd6e66d0290aa3387575ba9ccc51b
Tx public key: e9805c5063d8306e58e96cb46dd9d87b2f6313491e8c7b5b9a8eee8903480c68
Timestamp: 1710778731 Timestamp [UCT]: 2024-03-18 16:18:51 Age [y:d:h:m:s]: 01:040:07:57:17
Block: 981124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289811 RingCT/type: yes/0
Extra: 01e9805c5063d8306e58e96cb46dd9d87b2f6313491e8c7b5b9a8eee8903480c680211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2bd83df466eb245ee6a4964e08d1f23146d81c79bb3feb11224958abc65c109f 0.600000000000 1441217 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": 981134, "vin": [ { "gen": { "height": 981124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2bd83df466eb245ee6a4964e08d1f23146d81c79bb3feb11224958abc65c109f" } } ], "extra": [ 1, 233, 128, 92, 80, 99, 216, 48, 110, 88, 233, 108, 180, 109, 217, 216, 123, 47, 99, 19, 73, 30, 140, 123, 91, 154, 142, 238, 137, 3, 72, 12, 104, 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