Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5edafbaa7394ec7341855aa848eee2491e06aacd1ca7dfccc8ec1ba05b850923

Tx prefix hash: d464f47625006f96dbf93e260413b57c43f046b7a33a1c0373e86554d14fb24b
Tx public key: ed363ba18f7b6494ed051ce9a9e426173a8fb4eee2563fb988e8f7461cc9c804
Timestamp: 1710094564 Timestamp [UCT]: 2024-03-10 18:16:04 Age [y:d:h:m:s]: 01:242:17:07:16
Block: 975445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 432164 RingCT/type: yes/0
Extra: 01ed363ba18f7b6494ed051ce9a9e426173a8fb4eee2563fb988e8f7461cc9c8040211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a227acc67d66b32b34a8e9b9d41184b87bed95929e0b524fa6e8bfcabe8c12e 0.600000000000 1435416 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": 975455, "vin": [ { "gen": { "height": 975445 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a227acc67d66b32b34a8e9b9d41184b87bed95929e0b524fa6e8bfcabe8c12e" } } ], "extra": [ 1, 237, 54, 59, 161, 143, 123, 100, 148, 237, 5, 28, 233, 169, 228, 38, 23, 58, 143, 180, 238, 226, 86, 63, 185, 136, 232, 247, 70, 28, 201, 200, 4, 2, 17, 0, 0, 0, 2, 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