Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fde8e18a7cd54b6bc57cfc5a24e16bdaa68f1fcd1cea285dc404e7b5d2b3e1bf

Tx prefix hash: 0694b92facf6fca7fe06d0a57ae1a6e08b53da16be3109178d6d810cc87601a5
Tx public key: 9bf4436ed898d7979295173a41d4eba91b5e7d6f220a7729944205e026d9ca29
Timestamp: 1728818177 Timestamp [UCT]: 2024-10-13 11:16:17 Age [y:d:h:m:s]: 00:183:10:02:09
Block: 1130667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130878 RingCT/type: yes/0
Extra: 019bf4436ed898d7979295173a41d4eba91b5e7d6f220a7729944205e026d9ca29021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71124eee4c386911603a7f0b427f8f35d45ba52ccf8dedc027f833ff8d5475c1 0.600000000000 1613544 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": 1130677, "vin": [ { "gen": { "height": 1130667 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71124eee4c386911603a7f0b427f8f35d45ba52ccf8dedc027f833ff8d5475c1" } } ], "extra": [ 1, 155, 244, 67, 110, 216, 152, 215, 151, 146, 149, 23, 58, 65, 212, 235, 169, 27, 94, 125, 111, 34, 10, 119, 41, 148, 66, 5, 224, 38, 217, 202, 41, 2, 17, 0, 0, 0, 2, 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